-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create README.md #25
base: main
Are you sure you want to change the base?
Create README.md #25
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you @leoberhelman for working on this.
The structure looks good and the "TO BE ADDED" parts can be dealt with in the future.
Apart from the specific suggestions, as I mentioned in some comments, it might be useful to add some more detailed description and examples within each of the parsers.
README.md
Outdated
### change_date.py | ||
NEED TO ADD DESCRIPTION | ||
|
||
|
||
Currently these files only operate on Dump files and include a work around to deal with the river field grids. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
### change_date.py | |
NEED TO ADD DESCRIPTION | |
Currently these files only operate on Dump files and include a work around to deal with the river field grids. | |
### change_date | |
Change the date of a UM restart file. | |
Run `change_date --help` for detailed usage information. |
More information to be added within the parser, same as perturbIC
README.md
Outdated
Currently these files only operate on Dump files and include a work around to deal with the river field grids. | ||
|
||
## Installation | ||
DICUSS AT SOME POINT |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
DICUSS AT SOME POINT | |
TO BE ADDED |
README.md
Outdated
## Usage | ||
|
||
```python | ||
If the user wants to run perturbIC with a specific output filename | ||
python perturbIC input_file_path -a 0.01 -s 2234 -o output_file_path | ||
|
||
Otherwise it is optional perturbIC will create a filename from the input path | ||
python perturbIC input_file_path -a 0.01 -s 2234 | ||
|
||
The amplitude and seed are also optional as well | ||
python perturbIC input_file_path -a 0.01 -s 2234 | ||
|
||
To take a subset of field the user must provide a either a list of fields to exculde (-x) | ||
python um_fields_subset.py input_file_path -x 155,156,3100,3101 | ||
|
||
To take a subset of field the user must provide a either a list of fields to include (-v) | ||
python um_fields_subset.py input_file_path -v 155,156,3100,3101 | ||
|
||
Or you can choose to have the program to only include pronostics -p | ||
python um_fields_subset.py input_file_path -p | ||
|
||
These three options must be run seperately |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
## Usage | |
```python | |
If the user wants to run perturbIC with a specific output filename | |
python perturbIC input_file_path -a 0.01 -s 2234 -o output_file_path | |
Otherwise it is optional perturbIC will create a filename from the input path | |
python perturbIC input_file_path -a 0.01 -s 2234 | |
The amplitude and seed are also optional as well | |
python perturbIC input_file_path -a 0.01 -s 2234 | |
To take a subset of field the user must provide a either a list of fields to exculde (-x) | |
python um_fields_subset.py input_file_path -x 155,156,3100,3101 | |
To take a subset of field the user must provide a either a list of fields to include (-v) | |
python um_fields_subset.py input_file_path -v 155,156,3100,3101 | |
Or you can choose to have the program to only include pronostics -p | |
python um_fields_subset.py input_file_path -p | |
These three options must be run seperately |
Examples like these should instead be included directly within the related parser, so they show up when <function> --help
is run`.
Seperated the usage case
Add the usage for the change_dump_date
Co-authored-by: Davide Marchegiani <[email protected]>
Co-authored-by: Davide Marchegiani <[email protected]>
Co-authored-by: Davide Marchegiani <[email protected]>
Co-authored-by: Davide Marchegiani <[email protected]>
Co-authored-by: Davide Marchegiani <[email protected]>
Co-authored-by: Davide Marchegiani <[email protected]>
Co-authored-by: Davide Marchegiani <[email protected]>
This pull request handles the read me and the --help option with the specific instructions for singular functions